feat: Implement resource requirements for components #194

Copilot · 2026-01-28T19:44:16Z

Summary

Adds resource specification support for components to enable Ray actor resource allocation and Tuner placement group optimization.

Changes

Core Schema

Added Resource Pydantic class in plugboard_schemas.component with fields: cpu, gpu, memory (integer bytes), resources (custom dict)
Supports full SI prefix notation:
- Decimal SI: n, u, m, k, M, G, T, P, E (e.g., "250m" → 0.25, "5k" → 5000)
- Binary: Ki, Mi, Gi, Ti, Pi, Ei (e.g., "10Mi" → 10,485,760 bytes)
Default: cpu=0.001, others zero
Implements to_ray_options() for Ray actor configuration
Memory stored as integer bytes for precision

Component Integration

Extended Component.__init__() with optional resources parameter
Updated ComponentArgsDict, ComponentArgsSpec for YAML support
Resources auto-exported and reconstructed from configuration

Ray Execution

Modified RayProcess._create_component_actor() to apply resource requirements via ray.remote(**ray_options)
Falls back to default Resource() when unspecified
Import statements organized at top of file

Tuner Optimization

Added Tuner._calculate_placement_bundles() to aggregate component resources
Creates PlacementGroupFactory with tuner overhead (0.5 CPU) + component bundle
Import statements organized at top of file

Documentation

Added section in docs/examples/tutorials/running-in-parallel.md referencing resource requirements example
Python and YAML examples demonstrating resource specification

Usage Example

from plugboard.schemas import Resource

# Python API
component = MyComponent(
    name="worker",
    resources=Resource(cpu="2.5k", gpu=1, memory="512Mi")
)

# YAML config
resources:
  cpu: "500m"
  gpu: 1
  memory: "100Mi"
  resources:
    custom_accelerator: 2

Tests

Unit tests: Resource parsing with all SI prefixes, validation, Ray conversion
Integration tests: Component/ProcessSpec/Tuner scenarios
Manual verification (full test suite requires Ray dependencies)

Original prompt

This section details on the original issue you should resolve

<issue_title>feat: Implement resource requirements for components</issue_title>
<issue_description>### Summary

Users would like to be able to specify custom resource requirements on Component objects. These can be passed to Ray when a RayProcess is used or a Tuner object is run.

Requirements:

Must be able to specify Resource requirements for cpu, gpu, memory, resources. These should be defined as a Pydantic class in plugboard_schemas.

Must be able to specify resources as a numerical value, or as a string (to be validated by Pydantic), e.g. 250m for 0.25 or 10Mi for 1024 * 1024 * 10. resources should be a dictionary of string key, numerical value pairs.

Must be able to convert these requirements to their Ray equivalents, see https://docs.ray.io/en/latest/ray-core/api/doc/ray.actor.ActorClass.options.html, i.e. cpu = "250m" gets converted to num_cpus=0.25.

Must be able to pass a Resource to a Component when instantiating it. This will require changes to the Component and its schema, so that we can specify resource requirements in YAML config.

The default requirement should be {"cpu": 0.001}, to be used if the user does not provide anything.

Resource requirements should be passed to the actor options in RayProcess.

They should be used in the resource placement group inside Tuner.

Example

No response

Alternatives

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes feat: Implement resource requirements for components #193

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: toby-coleman <[email protected]>

toby-coleman · 2026-01-28T20:07:44Z

plugboard-schemas/plugboard_schemas/component.py

+    """Parse a resource value from string or number.
+
+    Supports:
+    - Direct numerical values: 1, 0.5, 2.0


@copilot Can you make this more general? For example by using/supporting any of the following suffixes:

suffixes = { 'n': 1e-9, 'u': 1e-6, 'm': 1e-3, # Decimal SI 'k': 1e3, 'M': 1e6, 'G': 1e9, 'T': 1e12, 'P': 1e15, 'E': 1e18, 'Ki': 1024, 'Mi': 1024**2, 'Gi': 1024**3, 'Ti': 1024**4, 'Pi': 1024**5, 'Ei': 1024**6 }

Done. Extended to support all decimal SI prefixes (n, u, m, k, M, G, T, P, E) and binary prefixes (Ki, Mi, Gi, Ti, Pi, Ei) in commit 9515154.

toby-coleman · 2026-01-28T20:09:09Z

plugboard-schemas/plugboard_schemas/component.py

+
+    cpu: float = 0.001
+    gpu: float = 0
+    memory: float = 0


Memory should be specified as an integer number of bytes

Done. Changed memory field type to int and added separate validator to cast to integer in commit 9515154.

toby-coleman · 2026-01-28T20:11:02Z

plugboard-schemas/plugboard_schemas/component.py

    initial_values: _t.NotRequired[dict[str, _t.Any] | None]
    parameters: _t.NotRequired[dict[str, _t.Any] | None]
    constraints: _t.NotRequired[dict[str, _t.Any] | None]
+    resources: _t.NotRequired["Resource | None"]


Suggested change

resources: _t.NotRequired["Resource | None"]

resources: _t.NotRequired[Resource | None]

Done in commit 9515154.

toby-coleman · 2026-01-28T20:14:39Z

plugboard/process/ray_process.py

-        ).remote(**args)
+
+        # Get resource requirements from component
+        from plugboard.schemas import Resource


Move this import to the top

Done. Moved Resource import to top of file in commit 9515154.

examples/tutorials/004_using_ray/resources-example.yaml

toby-coleman · 2026-01-31T09:30:23Z

plugboard/tune/tune.py

+        Returns:
+            List of resource bundles for Ray placement group.
+        """
+        from plugboard.schemas import Resource


Move this import to the top

Done. Moved Resource import to top of file in commit 9515154.

toby-coleman

@copilot see comments

…r, move imports to top Co-authored-by: toby-coleman <[email protected]>

Initial plan

4530341

Copilot AI assigned Copilot and toby-coleman Jan 28, 2026

Copilot started work on behalf of toby-coleman January 28, 2026 19:44 View session

Copilot AI and others added 4 commits January 28, 2026 19:49

Add Resource class and integrate with Component, RayProcess, and Tuner

d529dee

Co-authored-by: toby-coleman <[email protected]>

Add comprehensive tests for Resource implementation

f59376c

Co-authored-by: toby-coleman <[email protected]>

Add examples for resource requirements in Ray processes

0219833

Co-authored-by: toby-coleman <[email protected]>

Fix type annotations and address code review feedback

3ec7854

Co-authored-by: toby-coleman <[email protected]>

Copilot AI changed the title ~~[WIP] Add resource requirements for components~~ feat: Implement resource requirements for components Jan 28, 2026

Copilot finished work on behalf of toby-coleman January 28, 2026 20:01

Copilot AI requested a review from toby-coleman January 28, 2026 20:01

toby-coleman reviewed Jan 28, 2026

View reviewed changes

toby-coleman reviewed Jan 31, 2026

View reviewed changes

examples/tutorials/004_using_ray/resources-example.yaml Show resolved Hide resolved

toby-coleman reviewed Jan 31, 2026

View reviewed changes

toby-coleman requested changes Jan 31, 2026

View reviewed changes

Copilot started work on behalf of toby-coleman January 31, 2026 09:34 View session

Address code review feedback: generalize suffixes, make memory intege…

9515154

…r, move imports to top Co-authored-by: toby-coleman <[email protected]>

Copilot AI requested a review from toby-coleman January 31, 2026 09:38

Copilot finished work on behalf of toby-coleman January 31, 2026 09:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: Implement resource requirements for components #194

feat: Implement resource requirements for components #194

Uh oh!

Copilot AI commented Jan 28, 2026 •

edited

Loading

Uh oh!

toby-coleman Jan 28, 2026 •

edited

Loading

Uh oh!

Copilot AI Jan 31, 2026

Uh oh!

toby-coleman Jan 28, 2026

Uh oh!

Copilot AI Jan 31, 2026

Uh oh!

toby-coleman Jan 28, 2026

Uh oh!

Copilot AI Jan 31, 2026

Uh oh!

toby-coleman Jan 28, 2026

Uh oh!

Copilot AI Jan 31, 2026

Uh oh!

Uh oh!

toby-coleman Jan 31, 2026

Uh oh!

Copilot AI Jan 31, 2026

Uh oh!

toby-coleman left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	resources: _t.NotRequired["Resource \| None"]
	resources: _t.NotRequired[Resource \| None]

feat: Implement resource requirements for components #194

Are you sure you want to change the base?

feat: Implement resource requirements for components #194

Uh oh!

Conversation

Copilot AI commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Example

Alternatives

Comments on the Issue (you are @copilot in this section)

Uh oh!

toby-coleman Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

toby-coleman Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

toby-coleman Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

toby-coleman Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

toby-coleman Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

Uh oh!

toby-coleman left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Jan 28, 2026 •

edited

Loading

toby-coleman Jan 28, 2026 •

edited

Loading